Wireless load balancing across bands

ABSTRACT

A technique for wireless load balancing involves providing a wireless infrastructure that creates a target band option and helps push clients toward that band. An example of a method according to the technique involves, by way of example but not limitation, responding only to probe requests on a first band when a client is detected on the first band and a second band. For example, using the techniques described herein, a platform that is both 802.11a and 802.11b/g compliant may attempt to connect preferentially to the 802.11b/g band of a wireless network, and be migrated toward the 802.11a band instead.

BACKGROUND

Today, 802.11 wireless networks operate in two frequency bands.802.11b/g in the 2.4 GHz spectrum and 802.11a in the 5 GHz spectrum.802.11 wireless clients in most laptops and other devices are shippedwith 802.11b/g band as the default band. Indeed, the majority of 802.11devices are either only in the 802.11b/g band or are preferentially inthe 802.11b/g band. In a specific instance at a trade show, it was notedthat about 95% of devices at the trade show got onto the 802.11b/g bandeven though perhaps half of the devices were 802.11a-capable.Over-utilization of the 802.11b/g band can result in throughputdegradation and other problems.

It may be beneficial to move “all” 802.11a-capable devices to 802.11awireless band, and create room in the 802.11b/g band. Most 802.11 Wi-fiphones will be in 802.11b/g band for a long time to come. So moving allthe capable data services to the preferred band is welcome move forvoice services, so that there are more channels available, for Vo-Wifiservices. Moreover, 802.11a may actually have a faster data rate and ahigher capacity than the 802.11b/g band, making the 802.11a band evenmore desirable from a throughput standpoint. In addition, microwaves,cordless phones, and other interfering devices today primarily affectthe 2.4 GHz space. So moving normal data services to 802.11a canpotentially reduce interference.

Although it may be desirable to migrate wireless clients towards a bandthat is underutilized, it is not a trivial task and effort is currentlybeing expended to resolve the issues associated with this problem. Evenif one band is not necessarily favored, by chance or for other reasons,one band may become over-utilized. In this case, load balancing acrossthe bands may be of value to improve throughput. Proactive techniquesmay also be of value in ensuring bands are load balanced before the loadbecomes significantly unbalanced across the bands. On the other hand,migrating wireless clients preferentially from, for example, an802.11b/g band toward, for example, an 802.11a band can result inover-utilization of the 802.11a band, and a reduction in overallthroughput.

These are but a subset of the problems and issues associated with loadbalancing across bands of a wireless network, and are intended tocharacterize weaknesses in the prior art by way of example. Theforegoing examples of the related art and limitations related therewithare intended to be illustrative and not exclusive. For example, wirelessclients may use different protocols other than 802.11, potentiallyincluding protocols that have not yet been developed. However, the sameproblem of excess concentration of users on a single band may persist aslong as one band is preferred. Other limitations of the related art willbecome apparent to those of skill in the art upon a reading of thespecification and a study of the drawings.

SUMMARY

The following embodiments and aspects thereof are described andillustrated in conjunction with systems, tools, and methods that aremeant to be exemplary and illustrative, not limiting in scope. Invarious embodiments, one or more of the above-described problems havebeen reduced or eliminated, while other embodiments are directed toother improvements.

A technique for wireless band load balancing involves providing awireless infrastructure that creates a target band option and helpsmigrate clients toward that band. An example of a method according tothe technique involves, by way of example but not limitation, respondingonly to probe requests on a first band when a client is detected on thefirst band and a second band. This method may create a perception, onthe part of the client, that a network is only available on the firstband. For example, using the techniques described herein, a platformthat is both 802.11a and 802.11b/g compliant may attempt to connectpreferentially to the 802.11b/g band of a wireless network, and bemigrated toward the 802.11a band instead.

A system according to the technique may include, by way of example butnot limitation, a received strength signal indicator (RSSI) module, atargeting module, and a service set identifier (SSID) forwarding module.In a non-limiting embodiment, the RSSI module may determine a firstsignal strength of a platform on a first wireless band and a secondsignal strength of the platform on a second wireless band. In anon-limiting embodiment, the targeting module may determine that thefirst wireless band is a target band. In a non-limiting embodiment, theSSID forwarding module may respond to the platform on the target band.

The proposed system can offer, among other advantages, load balancingacross bands of a wireless network, which can result in increasedcapacity on all of the bands. These and other advantages of the presentinvention will become apparent to those skilled in the art upon areading of the following descriptions and a study of the several figuresof the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated in the figures. However,the embodiments and figures are illustrative rather than limiting; theyprovide examples of the invention.

FIG. 1 depicts a system including a wireless access domain.

FIG. 2 depicts a computer system for use in the system of FIG. 1.

FIG. 3 depicts a conceptual diagram an example of a system including aplatform operable on multiple wireless bands.

FIG. 4 depicts a graphic illustration in which an acceptable signalstrength threshold is met for two bands.

FIG. 5 depicts a flowchart of an example of a method for load balancinga wireless network.

FIG. 6 depicts a flowchart of an example of a method for wireless loadbalancing on 5 GHz and 2.4 GHz spectral bands.

FIG. 7 depicts an example of a wireless band load balancing device.

DETAILED DESCRIPTION

In the following description, several specific details are presented toprovide a thorough understanding of embodiments of the invention. Oneskilled in the relevant art will recognize, however, that the inventioncan be practiced without one or more of the specific details, or incombination with other components, etc. In other instances, well-knownimplementations or operations are not shown or described in detail toavoid obscuring aspects of various embodiments, of the invention.

FIG. 1 depicts a system 100 including a wireless access domain. Thesystem 100 includes a computer system 102, a network 104, and a wirelessaccess domain 106. The system 100 may or may not include multiplewireless access domains. The computer system 102 may be practically anytype of device that is capable of communicating with a communicationsnetwork, such as, by way of example but not limitation, a workstation.The network 104 may be practically any type of communications network,such as, by way of example but not limitation, the Internet. The term“Internet” as used herein refers to a network of networks which usescertain protocols, such as the TCP/IP protocol, and possibly otherprotocols such as the hypertext transfer protocol (HTTP) for hypertextmarkup language (HTML) documents that make up the World Wide Web (theweb). The physical connections of the Internet and the protocols andcommunication procedures of the Internet are well known to those ofskill in the art.

In a non-limiting embodiment, the computer system 102 may be running aprogram such as, by way of example but not limitation, ethereal, todecode, by way of example but not limitation, IEEE 802.11 standardpackets encapsulated in TZSP that are received from the wireless accessdomain 106. In a non-limiting embodiment, the computer system 102 isconnected to a wireless backbone network (not shown), either directly orindirectly through a wireless network.

In a non-limiting embodiment, the network 104 provides a Layer 2 pathfor Layer 3 traffic, preserving IP addresses, sessions, and other wiredLayer 3 attributes as users roam throughout the wireless access domain106. The network may or may not include a wireless backbone network, orbe connected directly or indirectly to a wireless backbone network.Communications between the computer system 102 and the wireless accessdomain 106 are, therefore, Layer 3 traffic tunneled through Layer 2.Advantageously, by tunneling Layer 3 traffic at Layer 2, users stayconnected with the same IP address and keep the same security andQuality of Service (QoS) policies from the wired network while they roamthe wireless side. Since Layer 3 attributes are maintained, mobiledevices that are connected to the wireless access domain 106 can retainpersistent identities.

The seven layers of the Open System Interconnection (OSI) model, ofwhich Layers 2 and 3 are a part, are well-known to those of skill in therelevant art, and are, therefore, not described herein in anysubstantial detail. It should be noted, however, that Layer 3 is knownas the “Network Layer” because it provides switching and routingtechnologies, creating logical paths, known as virtual circuits, fortransmitting data from node to node. Routing and forwarding arefunctions of this layer, as well as addressing, internetworking, errorhandling, congestion control and packet sequencing. Layer 2 is known asthe “Data Link Layer” because at Layer 2 data packets are encoded anddecoded into bits; and Layer 2 furnishes transmission protocol knowledgeand management and handles errors in the physical layer, flow controland frame synchronization. The data link layer is divided into twosublayers: The Media Access Control (MAC) layer and the Logical LinkControl (LLC) layer. The MAC sublayer controls how a computer on thenetwork gains access to the data and permission to transmit it. The LLClayer controls frame synchronization, flow control, and error checking.

In non-limiting embodiments, the wireless access domain 106 may bereferred to as, by way of example but not limitation, a Local AreaNetwork (LAN), virtual LAN (VLAN), and/or wireless LAN (WLAN). Thewireless access domain 106 gives each user a persistent identity thatcan be tracked and managed, no matter where they roam. The wirelessaccess domain 106 may have one or more associated snoop filters. In anembodiment, the wireless access domain 106 may include one or moreradios.

In the example of FIG. 1, the wireless access domain 106 includes accessareas 108-1 to 108-N (hereinafter collectively referred to as accessareas 108). The access areas 108 have characteristics that depend upon,among other things, a radio profile. A radio profile is a group ofparameters such as, by way of example but not limitation, beaconinterval, fragmentation threshold, and security policies. In anembodiment, the parameters may be configurable in common across a set ofradios in one or more access areas 108. In another embodiment, a fewparameters, such as the radio name and channel number, must be setseparately for each radio. An example of the implementation of awireless access domain, provided by way of example but not limitation,includes a Trapeze Networks “identity-aware” Mobility Domain™.

In the example of FIG. 1, the following elements are associated witheach of the access areas 108: Wireless exchange switches 110-1 to 110-N(hereinafter collectively referred to as wireless exchange switches110), networks 112-1 to 112-N (hereinafter collectively referred to asnetworks 112), and access points 114-1 to 114-N (hereinaftercollectively referred to as access points 114).

In an embodiment, the wireless exchange switches 110 swap topology dataand client information that details each user's identity, location,authentication state, VLAN membership, permissions, roaming history,bandwidth consumption, and/or other attributes assigned by, by way ofexample but not limitation, an Authentication, Authorization, andAccounting (AAA) backend (not shown). In an embodiment, the wirelessexchange switches 110 provide forwarding, queuing, tunneling, and/orsome security services for the information the wireless exchangeswitches 110 receive from their associated access points 114. In anotherembodiment, the wireless exchange switches 110 coordinate, provide powerto, and/or manage the configuration of the associated access points 114.An implementation of a wireless exchange switch, provided by way ofexample but not limitation, includes a Trapeze Networks MobilityExchange™ switch. The Trapeze Networks Mobility Exchange™ switches may,in another implementation, be coordinated by means of the Trapeze AccessPoint Access (TAPA) protocol.

In an embodiment, the networks 112 are simply wired connections from thewireless exchange switches 110 to the access points 114. The networks112 may or may not be part of a larger network. In a non-limitingembodiment, the networks 112 provides a Layer 2 path for Layer 3traffic, preserving IP addresses, sessions, and other wired Layer 3attributes as users roam throughout the wireless access domain 106.Advantageously, by tunneling Layer 3 traffic at Layer 2, users stayconnected with the same IP address and keep the same security andQuality of Service (QoS) policies from the wired network while they roamthe wireless side.

In a non-limiting embodiment, the access points 114 are hardware unitsthat act as a communication hub by linking wireless mobile 802.11stations such as PCs to a wired backbone network. In an embodiment, theaccess points 114 connect users to other users within the network and,in another embodiment, can serve as the point of interconnection betweena WLAN and a fixed wire network. The number of users and size of anetwork help to determine how many access points are desirable for agiven implementation. An implementation of an access point, provided byway of example but not limitation, includes a Trapeze Networks MobilitySystem™ Mobility Point™ (MP™) access point.

The access points 114 are stations that transmit and receive data (andmay therefore be referred to as transceivers) using one or more radiotransmitters. For example, an access point may have two associatedradios, one which is configured for IEEE 802.11a standard transmissions,and the other which is configured for IEEE 802.11b standardtransmissions. In a non-limiting embodiment, an access point transmitsand receives information as radio frequency (RF) signals to and from awireless client over a 10/100BASE-T Ethernet connection. The accesspoints 114 transmit and receive information to and from their associatedwireless exchange switches 110. Connection to a second wireless exchangeswitch provides redundancy.

A station, as used herein, may be referred to as a device with a mediaaccess control (MAC) address and a physical layer (PHY) interface to thewireless medium that comply with the IEEE 802.11 standard. As such, in anon-limiting embodiment, the access points 114 are stations. Similarly,a wireless client 116 and a wireless client 118, which, in the exampleof FIG. 1, are depicted for illustrative purposes in the access area108-1, may be implemented as stations. In alternative embodiments, astation may comply with a different standard than IEEE 802.11, and mayhave different interfaces to a wireless or other medium.

In the example of FIG. 1, the wireless client 116 and the wirelessclient 118 are connected to the wireless network through the accesspoint 114-1. For illustrative purposes, the wireless connections of thewireless client 116 and the wireless client 118 are different. Forexample, the wireless client 116 may be connected to the wirelessnetwork over an 802.11a band, while the wireless client 118 may beconnected to the wireless network over an 802.11b/g band. Although FIG.1 is not intended to reflect a physical system but rather serve as aconceptual drawing, the wireless client 118 is assumed to be physicallyfurther from the access point 114-1 than the wireless client 116.

In operation, the system 100 may incorporate received strength signalindicator (RSSI) tracking to make clients that are physically far fromany access point to associate in the 802.11b/g band even if the clientsare heard on the 802.11a band. Alternatively, the physically distantclients may associated in the 802.11b/g band if they are not heard asgood on the 802.11a band. This may prevent clients that have weaker802.11a implementations and that are physically on the outer fringes ofwireless networks to still be able to connect to the network and use thenetwork effectively. RSSI tracking is but one example of how to keepclients that are physically distant from an access point to associatein, for example, the 802.11b/g band.

FIG. 2 depicts a computer system 200 for use in the system 100 (FIG. 1).The computer system 200 may be a conventional computer system that canbe used as a client computer system, such as a wireless client or aworkstation, or a server computer system. The computer system 200includes a computer 202, I/O devices 204, and a display device 206. Thecomputer 202 includes a processor 208, a communications interface 210,memory 212, display controller 214, non-volatile storage 216, and I/Ocontroller 218. The computer 202 may be coupled to or include the I/Odevices 204 and display device 206.

The computer 202 interfaces to external systems through thecommunications interface 210, which may include a modem or networkinterface. It will be appreciated that the communications interface 210can be considered to be part of the computer system 200 or a part of thecomputer 202. The communications interface 210 can be an analog modem,ISDN modem, cable modem, token ring interface, satellite transmissioninterface (e.g. “direct PC”), or other interfaces for coupling acomputer system to other computer systems.

The processor 208 may be, for example, a conventional microprocessorsuch as an Intel Pentium microprocessor or Motorola power PCmicroprocessor. The memory 212 is coupled to the processor 208 by a bus220. The memory 212 can be Dynamic Random Access Memory (DRAM) and canalso include Static RAM (SRAM). The bus 220 couples the processor 208 tothe memory 212, also to the non-volatile storage 216, to the displaycontroller 214, and to the I/O controller 218.

The I/O devices 204 can include a keyboard, disk drives, printers, ascanner, and other input and output devices, including a mouse or otherpointing device. The display controller 214 may control in theconventional manner a display on the display device 206, which can be,for example, a cathode ray tube (CRT) or liquid crystal display (LCD).The display controller 214 and the I/O controller 218 can be implementedwith conventional well known technology.

The non-volatile storage 216 is often a magnetic hard disk, an opticaldisk, or another form of storage for large amounts of data. Some of thisdata is often written, by a direct memory access process, into memory212 during execution of software in the computer 202. One of skill inthe art will immediately recognize that the terms “machine-readablemedium” or “computer-readable medium” includes any type of storagedevice that is accessible by the processor 208 and also encompasses acarrier wave that encodes a data signal.

The computer system 200 is one example of many possible computer systemswhich have different architectures. For example, personal computersbased on an Intel microprocessor often have multiple buses, one of whichcan be an I/O bus for the peripherals and one that directly connects theprocessor 208 and the memory 212 (often referred to as a memory bus).The buses are connected together through bridge components that performany necessary translation due to differing bus protocols.

Network computers are another type of computer system that can be usedin conjunction with the teachings provided herein. Network computers donot usually include a hard disk or other mass storage, and theexecutable programs are loaded from a network connection into the memory212 for execution by the processor 208. A Web TV system, which is knownin the art, is also considered to be a computer system, but it may lacksome of the features shown in FIG. 2, such as certain input or outputdevices. A typical computer system will usually include at least aprocessor, memory, and a bus coupling the memory to the processor.

In addition, the computer system 200 is controlled by operating systemsoftware which includes a file management system, such as a diskoperating system, which is part of the operating system software. Oneexample of operating system software with its associated file managementsystem software is the family of operating systems known as Windows®from Microsoft Corporation of Redmond, Wash., and their associated filemanagement systems. Another example of operating system software withits associated file management system software is the Linux operatingsystem and its associated file management system. The file managementsystem is typically stored in the non-volatile storage 216 and causesthe processor 208 to execute the various acts required by the operatingsystem to input and output data and to store data in memory, includingstoring files on the non-volatile storage 216.

Some portions of the detailed description are presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

The present invention, in some embodiments, also relates to apparatusfor performing the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina computer readable storage medium, such as, but is not limited to,read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, any type of disk including floppydisks, optical disks, CD-ROMs, and magnetic-optical disks, or any typeof media suitable for storing electronic instructions, and each coupledto a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description below.In addition, the present invention is not described with reference toany particular programming language, and various embodiments may thus beimplemented using a variety of programming languages.

FIG. 3 depicts a conceptual diagram an example of a system 300 includinga platform operable on multiple wireless bands. In the example of FIG.3, the system 300 includes a wireless access point 302, a single-bandplatform 304, a moveable platform 306, and a plurality of platforms308-1 to 308-N (referred to collectively as platforms 308). The moveableplatform 306 is depicted in 5 dashed boxes 306-1 to 306-5. As will bedescribed, the moveable platform 306 is so depicted in order to explainchanges over time.

In the example of FIG. 3, the single-band platform 304 is connected to awireless network through the wireless access point 302. The single-bandplatform 304 may, depending upon the embodiment, implementation, ordevice, be capable of connecting only on a single band such as, by wayof example but not limitation, the 802.11b/g band. Alternatively, thesingle-band platform 304 may be sending and/or receiving data that wouldoperate most effectively on a single band of a multi-band network. Forexample, VoIP is preferentially performed on the 802.11b/g band, asopposed to the 802.11a band. Thus, the characterization of thesingle-band platform 304 may be a self-imposed characterization (e.g.,the single-band platform 304 only attempts to connect over a preferredband).

In the example of FIG. 3, the platform 306 is depicted as changing overtime (platform 306-1 to 306-5). At the time period associated with306-1, the platform 306 is connected to the wireless network over afirst band. The first band may be a preferred band (e.g., some devicesthat are multi-band capable preferentially attempt to connect over the802.11b/g band). Alternatively, the first band may have a strongerassociated signal.

FIG. 4 depicts a graphic illustration 400 in which an acceptable signalstrength threshold is met for two bands. In the example of FIG. 4, thefirst band 402 has a wider radius of coverage from a central point 406,which may be an access point, compared to the radius of coverage of asecond band 404. By way of example but not limitation, the first band402 may be an 802.11b/g band and the second band 404 may be an 802.11aband. 802.11b/g typically has a larger radius of coverage compared to802.11a for reasons, such as data rate associated with the bands, thatare known to one of skill in the art. It may be noted that the firstband 402 and the second band 404 could have different coverage based onother factors including, but not limited to, interference in one of thebands, an environment that relatively favors one band, a weakertransmitter or receiver on one of the bands (either on the platform orat the wireless access point), or some other factor.

Referring once again to FIG. 3, at the time period associated with306-2, the platform 306 remains connected via the first band, butsignals are sent over a second band. It may be noted that the signalsmay have been sent during the time period associated with 306-1 as well,but a distinction is drawn for illustrative purposes only. The accesspoint 302 (or some device higher up, such as a switch or a server)determines whether a connection should be made via the first band or thesecond band. The determination may be based on, for example, whether itis desirable to keep the first band as clear as possible of traffic sothat the single-band platform 304 can connect via the first band, theamount of traffic on the first and second bands from the platforms 308,the RSSI of the platform 306 is higher on the first band or the secondband, or other factors, or a combination of factors. In an embodiment,the time period associated with 306-2 lasts for a predetermined periodof time, although the period of time may be dynamic (e.g., quicker whenRSSI changes rapidly or quicker if traffic is exceptionally heavy on oneband or the other) or arbitrary.

In the example of FIG. 3, when the access point 302 has heard, forexample, probe requests from the platform 306 for a period of time, atthe time period associated with 306-3, the platform 306 is connected viathe second band, and the access point 302 may stop responding to proberequests on the first band. When the access point 302 stops respondingto the platform 306 on the first band, this simulates to the platform306 as if a service set identifier (SSID) associated with the secondband is the only one being offered. As is known in the relevant art, aSSID is a sequence of characters that uniquely names a WLAN.

In an embodiment, the platforms 308 are connected to the wirelessnetwork over the first band if possible, and over the second band if faraway or if the platform is single-band only. It should be noted thatthis is not necessarily a bad thing. For example, if the second band is802.11b/g and the first band is 802.11a, measurements of throughput haveshown that devices today tend toward the 802.11b/g band and some devicesare not capable of accessing the 802.11a band. It is estimated that evenif the migration is performed toward 802.11a when signal strength isgood, throughput may be maintained, in many instances, at a reasonablelevel.

In the example of FIG. 3, at the time period associated with 306-4, theaccess point 302 entertains the option of enabling the platform 306 toswitch from the first band back to the second band. For example, theplatform at the time period associated with 306-4 may have poor signalquality on the first band. Again, the access point 302 (or some otherdevice) may consider multiple factors when deciding whether switchingback to the second band is appropriate. For example, the access point302 may be able to determine that the platform 306 is on the fringe ofthe radius of coverage of the first band by comparing RSSI values to arange of acceptable values. If the platform 306 drops below anacceptable RSSI threshold, the access point 302 can, potentiallyseamlessly, enable probe responses on the second band.

It may be noted that the RSSI threshold may be a static or dynamicvalue. By way of example but not limitation, the RSSI threshold may bethe highest RSSI value other than the current band. In such anembodiment, the RSSI value could remain relatively steady over time, butthe RSSI threshold could rise, causing the RSSI value to becomeunacceptable.

In the example of FIG. 3, at the time period associated with 306-5, theplatform 306 is back on the second band. In the near future, it ispredicted that VoIP wireless devices will continue to dominate the802.11b/g band. Advantageously, this technique can migrate non-VoIPdevices away from the 802.11b/g band, freeing up the band for VoIP.However, as previously mentioned, it may be desirable to allow access bynon-VoIP devices under certain circumstances (e.g., the devices do notexceed an acceptable RSSI threshold on the other band or bands) thathave just been described with reference to FIG. 3.

Although the techniques have been described with respect to two bands,802.11a and 802.11b/g, where 802.11a is the target band to which devicesare migrated, the techniques could be used in conjunction with a third(fourth, etc.) band. For more than two protocols, devices may bemigrated toward a target band of the more than two bands. In certaincases, devices may be unable to migrate toward the target band (e.g.,because the devices are not capable of operating on the target band) ormigration toward the target band is undesirable (e.g., because of signalstrength, data rate, and/or other factors). Although the techniques havebeen described with respect to two bands, 802.11a and 802.11b/g, thetechniques could be used in conjunction with a different standard (ortwo or more protocols). For protocols other than 802.11, the techniqueis readily applicable.

In an embodiment, one of the factors used in load balancing may beaccess point occupancy. For example, access points may have overlappingareas of coverage. If it is determined that a first access point isbusier than a second access point, the system may preferentially migratethe platform from the first access point to the second access point.

In an embodiment, the target band is adjustable. For example, if it isdetermined that a band other than the target band would be moreadvantageous as a target band, then the other band can be set as thetarget band. As before, certain characteristics of non-target bands mayoverride the preference (e.g., if signal strength does not exceed anacceptable RSSI threshold, or if the data is of a particular type).

FIG. 5 depicts a flowchart 500 of an example of a method for loadbalancing a wireless network. This method and other methods are depictedas serially arranged modules. However, modules of the methods may bereordered, or arranged for parallel execution as appropriate. FIG. 5 isintended to illustrate a first example of operation of a system such asthat depicted in FIG. 3, using the techniques described herein. In theexample of FIG. 5, the flowchart is arranged such that, in general,modules associated with a platform are on the left-hand side and modulesassociated with an access point are on the right-hand side. Thisorganization is for illustrative purposes only.

In the example of FIG. 5, the flowchart 500 starts at module 502 where afirst probe request is sent from the platform on a first band, and asecond probe request is sent from the platform on a second band.Implicit in module 502 is that the platform is capable of sending proberequests on at least two bands. However, the platform may be capable ofoperating on more than two bands, and may therefore send probe requestson more than two bands.

In the example of FIG. 5, the flowchart 500 continues to module 504where the first probe request is received at the access point on thefirst band, and the second probe request is received at the access pointon the second band. Implicit in module 504 is that the access point iscapable of sending probe request on at least two bands. However, theplatform may be capable of operating on more than two bands, and may ormay not receive probe requests on more than two bands. It should benoted that an access point could be configured to operate on only oneband. In such a case, multiple access points capable of operation onmultiple bands could be used together to gain at least some of theadvantages associated with this technique.

In the example of FIG. 5, the flowchart 500 continues to module 506where the access point determines the target band. The target band maybe determined in a number of ways. For example, a human or softwareagent may arbitrarily (or for reasons not considered by the system)select a target band. As another example, the target band may beselected using network traffic considerations such as congestion on oneor more bands, available bandwidth on one or more of the bands, high orlow throughput on one or more of the bands, etc. As another example, thetarget band may be selected on a platform-by-platform basis, such asbased upon signal strengths associated with a platform on the variousbands.

In the example of FIG. 5, the flowchart 500 continues to decision point508 where it is determined whether to target the first band. It shouldbe noted that the example of FIG. 5 describes only a first and secondband, but the target band could be chosen from any number of bands. Ifit is determined that the first band is the target band (508-Yes), thenthe flowchart continues to module 510 where the access point responds tothe first probe request on the first band, and refuses to respond to thesecond probe request on the second band. If, on the other hand, it isdetermined that the second band is the target band (508-No), then theflowchart continues to module 512 where the access point refuses torespond to the first probe request on the first band, and responds tothe second probe request on the second band.

In the example of FIG. 5, the flowchart 500 continues to module 514where the response to probe request is received at the platform on thetarget band. Depending upon the determination at module 506, the targetband may be either the first band or the second band. It should be notedthat since the platform only received a response to probe request on thetarget band, and not the other band, from the perspective of theplatform, only the target band is currently available.

In the example of FIG. 5, the flowchart 500 continues to module 516where a connection is established on the target band. The connection maybe established between the platform and the access point by any known orconvenient protocol, procedure, or means.

In the example of FIG. 5, the flowchart 500 continues to decision point518 where it is determined whether to select a new target band. Thedetermination may be based on factors similar to those described withrespect to module 506. By way of example but not limitation, it may bedesirable to select a new target band if a detected signal strength onthe target band drops below an acceptable signal strength threshold, orif the signal strength on the target band is lower than on a non-targetband by a certain margin. If it is determined that an attempt to selecta new target band should be made (518-Yes), then the flowchart 500returns to the beginning (module 502) and proceeds as described above.If, on the other hand, it is determined that an attempt to select a newtarget band should not be made (518-No), then the flowchart 500continues to module 520 where the connection is maintained on the targetband, and the flowchart returns to decision point 518 and repeats untilit is determined that an attempt should be made to select a new targetband, if ever.

FIG. 6 depicts a flowchart 600 of an example of a method for wirelessload balancing on 5 GHz (which may or may not include an 802.11b/g band)and 2.4 GHz (which may or may not include an 802.11a band) spectrumbands. The flowchart 600 begins at module 602 where an approximately 5GHz spectrum band is set as a target band. The setting of the targetband may be based upon any known or convenient load balancingconsiderations including but not limited to traffic characteristics onthe various bands, platform characteristics, access pointcharacteristics, or other characteristics. In an embodiment, the targetband can be changed at a later time.

In the example of FIG. 6, the flowchart 600 continues to decision point604 where it is determined whether a detected signal on the target bandis higher than an RSSI threshold. If not (604-No), the flowchart 600repeats decision point 604 until this condition is true, if ever. If, onthe other hand, it is determined that the detected signal on the targetband is higher than the RSSI threshold (604-Yes), then the flowchart 600continues to module 606 where a client associated with the detectedsignal strength is migrated from the 2.4 GHz spectrum band to the targetband. In an embodiment that includes multiple other bands (besides the2.4 GHz spectrum band), the migration may be carried out for clients onthose other bands. In another embodiment, all clients that arecompatible with the target band may be migrated from the 2.4 GHzspectrum band to the target band if the respective detected signalstrengths exceed the RSSI threshold.

In the example of FIG. 6, the flowchart 600 continues to decision point608 where it is determined whether a detected signal on the target bandhas dropped below the RSSI threshold. If not (608-No), then theflowchart 600 repeats decision point 608 until this condition is true,if ever. If, on the other hand, it is determined that the detectedsignal on the target band has dropped below the RSSI threshold(608-Yes), then the flowchart 600 continues to module 610 where theclient is switched back to the 2.4 GHz spectrum band. At this point, theflowchart 600 ends. Of course, depending upon the embodiment and/orimplementation, the client could presumably switch between bands anynumber of times.

In an embodiment, the method may further include disabling the migratingand switching based upon network traffic characteristics. For example,congestion on one or more bands may result in an override of the signalstrength-dependent migration.

FIG. 7 depicts an example of a wireless band load balancing device 700.The device 700 may be, by way of example but not limitation, a wirelessaccess point. In the example of FIG. 7, the device 700 includes aprocessor 702, memory 704, and radios 706-1 to 706-N (referred tocollectively as radios 706), coupled to a bus 708. It may be noted thatthe bus architecture is optional, and is selected for ease ofillustration, but any applicable known or convenient architecture wouldsuffice.

In the example of FIG. 7, the memory 704, which may include volatileand/or non-volatile storage, or software, firmware, and/or hardwarecomponents, includes an RSSI module 712, a targeting module 714, and anSSID forwarding module 716. While the modules 712, 714, and 716 aredepicted as residing locally on the device 700, one, some, or all of themodules could instead be located on another remote device, such as aswitch, a server, or some other computer.

In the example of FIG. 7, the radios 706 are intended to representradios on different bands. However, a single radio could be used tocover multiple bands, or multiple radios could cover a single band,depending upon implementation. For illustrative purposes only, it isassumed that the radios 706 are associated with different bands.

In operation, the radios 706 receive signals from platforms (not shown).The signals are evaluated by the RSSI module to determine the strengthof the signals. It may be noted that since the RSSI module typicallyreceives a subset of all signals sent by the platforms, so the RSSIvalue associated with a signal is an estimation of actual averagesignals strength. In general, the larger the sample, the greater theaccuracy. Each signal has an RSSI value. For example, if a platform hassignals sampled on each of the bands, each of the signals have an RSSIvalue. If multiple signals associated with a platform are sampled on asingle band, the RSSI value may be an average of the signals.

In operation, the targeting module 714 determines which band is atargeted band. The determination may be made by assignment,consideration of traffic characteristics, using RSSI values on aplatform-by-platform basis, or by some other means or combination. Forexample, if the targeting module 714 determines the target band based onRSSI values for a platform on the various bands, the targeting module714 may select the band with the highest associated RSSI values as thetarget band. As another example, the targeting module 714 may requirethat certain bands have a higher associated RSSI value by a margin. Asanother example, RSSI values may be weighted depending upon trafficcharacteristics of the associated bands.

In operation, when the targeting module 714 establishes a target band,the SSID forwarding module 716 sends a message, through the associatedradio, to the relevant platform. For example, the SSID forwarding module716 may respond to probe requests from a platform on the target band.Notably, in an embodiment that uses probe requests, the SSID forwardingmodule 716 refuses to response to probe requests on non-target bands.Thus, the platform will believe it has only a single choice—the targetband.

It may be noted that the description above applies to platforms that areattempting to connect to a wireless network for the first time, orattempting to reconnect. For example, the RSSI module may determine thatRSSI values are higher on a first band initially, the first bandbecoming the target band, but that RSSI values are higher on a secondband later, and change the target band to the second band in response.

As used herein, a wireless network refers to any type of wirelessnetwork, including but not limited to a structured network or an ad hocnetwork. Data on a wireless network is often encrypted. However, datamay also be sent in the clear, if desired. With encrypted data, a roguedevice will have a very difficult time learning any information (such aspasswords, etc.) from clients before countermeasures are taken to dealwith the rogue. The rogue may be able to confuse the client, and perhapsobtain some encrypted data, but the risk is minimal (even less than forsome wired networks).

As used herein, the term “embodiment” means an embodiment that serves toillustrate by way of example but not limitation.

It will be appreciated to those skilled in the art that the precedingexamples and embodiments are exemplary and not limiting to the scope ofthe present invention. It is intended that all permutations,enhancements, equivalents, and improvements thereto that are apparent tothose skilled in the art upon a reading of the specification and a studyof the drawings are included within the true spirit and scope of thepresent invention. It is therefore intended that the following appendedclaims include all such modifications, permutations and equivalents asfall within the true spirit and scope of the present invention.

1. A method comprising: receiving from a wireless device a first probe request on a first band and a second probe request on a second band; responding to the first probe request on the first band; refusing to respond to the second probe request on the second band; wherein responding to the first probe request and refusing to respond to the second probe request creates an impression at the wireless device that a service set identifier (SSID) is unavailable on the second band.
 2. The method of claim 1, further comprising connecting the wireless device to a wireless network on the second band if a received strength signal indicator (RSSI) on the first band is below an acceptable signal threshold.
 3. The method of claim 1, further comprising connecting the wireless device to a wireless network on the first band after creating the impression at the wireless device that the SSID is unavailable on the second band.
 4. The method of claim 1, wherein the SSID is a first SSID, further comprising, in response to a received strength signal indicator (RSSI) on the first band dropping below an acceptable signal threshold: responding to a third probe request on the second band; refusing to respond to a fourth probe request on the first band; wherein the responding to the third probe request and refusing to respond to the fourth probe request creates an impression at the wireless device that a second SSID is unavailable on the first band.
 5. The method of claim 4, wherein the first SSID and the second SSID are identical.
 6. The method of claim 1, wherein the refusing to respond to the second probe request is in response to congestion on the second band.
 7. The method of claim 1, wherein the refusing to respond to the second probe request is in response to detection of a stronger signal on the first band than on the second band.
 8. The method of claim 1, wherein the refusing to respond to the second probe request is an attempt to load balance across the first band and the second band.
 9. The method of claim 1, further comprising determining that the first band is a target band using available data.
 10. The method of claim 1, further comprising selecting the first band as a target band.
 11. The method of claim 1, further comprising accepting input that the first band is a target band.
 12. A method comprising: setting an approximately 5 GHz spectrum band as a target band; migrating a client that is compatible with the target band from an approximately 2.4 GHz spectrum band to the target band if a first detected signal strength associated with the client exceeds a received strength signal indicator (RSSI) threshold; switching the client back to the approximately 2.4 GHz spectrum band if a second detected signal strength associated with the client drops below the RSSI threshold.
 13. The method of claim 12, further comprising changing the target band.
 14. The method of claim 12, further comprising migrating from another band to the target band.
 15. The method of claim 12, further comprising migrating all clients that are compatible with the target band from the approximately 2.4 GHz spectrum band to the target band if respective detected signal strengths exceed the RSSI threshold.
 16. The method of claim 12, further comprising disabling said migrating and said switching back based upon network traffic characteristics.
 17. The method of claim 12, wherein the approximately 5 GHz spectrum band is an 802.11b/g band.
 18. The method of claim 12, wherein the approximately 2.4 GHz spectrum band is an 802.11a band.
 19. A system comprising: memory having executable modules stored therein; a processor coupled to the memory and capable of executing the executable modules stored in the memory; a first radio, coupled to the memory, associated with a first wireless band; a second radio, coupled to the memory, associated with a second wireless band; said memory including: a received strength signal indicator (RSSI) module for determining a first signal strength of a platform on the first wireless band and a second signal strength of the platform on the second wireless band; a targeting module for determining that the first wireless band is a target band; a service set identifier (SSID) forwarding module for responding to the platform on the target band; wherein, in operation, the platform is unaware the second band is available and accordingly connects on the first band.
 20. The system of claim 19, wherein the platform is capable of connecting on either the first band or the second band. 